-
Notifications
You must be signed in to change notification settings - Fork 24.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs(core): change from deprecated renderer to renderer2 #19920
Conversation
We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for the commit author(s). If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google. |
Added alternate email to google account |
CLAs look good, thanks! |
Linting and tests seem to fail unrelated to my changes, is there anything i should be doing? |
The tests where flakes and the linting errors are indeed not related to this PR. |
We now show the proper class instead of the deprecated Renderer Fixes angular#19806
d3cfae2
to
bf81d04
Compare
@gkalpak Done :) |
You can preview f944085 at https://pr19920-f944085.ngbuilds.io/. |
LGTM but someone from the |
Accidentally introduced in angular#19920, where other linting errors (unrelated to the PR) prevented proper linting.
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
We now show the proper class instead of the deprecated Renderer
Fixes #19806 (link)
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
ElementRef Documentation links to deprecated Renderer class
Issue Number: 19806
What is the new behavior?
It now links to Renderer2 class instead of the deprecated Renderer class
Does this PR introduce a breaking change?
Other information